|
|
| Author |
Thread Statistics | Show CCP posts - 7 post(s) |
A Brr
   |
Posted - 2006.03.02 18:34:00 -
[1]
Installing a T2 manufacturing job stucks at "installing job"
|
A Brr
|
Posted - 2006.03.04 08:38:00 -
[2]
One more issue: Agression coutdown timer resets to full on various things, for example undocking from station.
Example, doing Mission I, have to kill Sanshas, get Agression Countdown cs. True Power. Collect loot, dock. Before undock Counter was down to below 1m. After undock it is back to 15m. After mission II (unauthorized military pressence) where i have to kill Minmatar fleet, The counter vs. republic fleet is 12m, True Power 13m ?!
|
A Brr
|
Posted - 2006.03.04 09:25:00 -
[3]
forum also broken? When i edit my post, i get the message "Thread does not exist" - but the post is changed?
|
A Brr
|
Posted - 2006.03.04 11:47:00 -
[4]
Not direct related to this patch, but still anoying: When docking at a station and opening the corp hangar, always hangar 1 opens first, after the hangar has loaded, the last opened hangars loads. Skip that loading of hangar 1, opening corp hangars is low enough, no need for doing it with 2 different hangars.
|
A Brr
|
Posted - 2006.03.04 12:15:00 -
[5]
Server still starting up, so one more: When rightclicking a BP in a corp-hangar for the first time after a session change the popup menue takes about 15..30s to show up.
Steps to reproduce:
1 Get a session change (eg. dock at the station, log in)
2 Open the corp hangar and wait a long time (see above)until it has loaded
3 Right klick on a BP in the corp hangar, count the seconds until the pop-up window shows up
|
A Brr
|
Posted - 2006.03.04 12:35:00 -
[6]
Edited by: A Brr on 04/03/2006 12:36:44
CCP Valar explained here http://oldforums.eveonline.com/?a=topic&threadID=302502&page=3
how the travel warning system works, and why there are issues with it atm.
 Originally by: Akhual
Not sure if this has been mentioned, but the new traffic reports appear to be interfering with autopilot.
I set autopilot to a system a simple 8 jumps away, and again and again it refused to let me go bacause one system on report was reported to be having problems.
So, I simply jumped manually, and arrived at my destination with no problems (every system on the route was empty).
To test, I went back to my start system and reset the autopilot - and agian it said one system on the route was blcoked and thus autopilot could not be used.
I set the autopilot for one system shorter than the destination (ie, set the destination for the system before my goal) and it worked fine. It was simply the last system it did not like.
Just to repeat - manually jumping into that system was fine - and it was completley empty when i got there.
I won't name the system here for security reasons (I don't like people knowing where I am without paying lol!). If system name is needed let me know and I'll post it under 'my questions'.
|
A Brr
|
Posted - 2006.03.04 14:08:00 -
[7]
Return to drohnebay still doesn't work for Vespa II and a Raven. From 5 drohne most of the time only 4 make it to the drohnebay, sometimes only 3 of 5 manage to get in.
Originally by: R3dSh1ft
Drones since bloodlines = 10 THUMBS UP!!
Thanks for listening and modifying the code
Luv ya for it
|
A Brr
|
Posted - 2006.03.05 10:26:00 -
[8]
When your travelling and browsing your wallet/market and one of the transactions in wallet / market hasn't completed (eg. market window still loading) and the autopilot jumps out, you have to relog to finish the jump.
|
A Brr
|
Posted - 2006.03.05 11:30:00 -
[9]
Originally by: Marquain Calleur
Disappointing.
I have to say that the Blood patch has revealed once again that CCP is not properly prepared to handle the QA process.
A few errors are always to be expected, but I think anyone will agree that the above reflects more than that. This patch was not properly tested before it was released.
While I think most people appreciate the hard word CCP does to remedy the situation, it has to be said also that they brought this upon themselves. We did not.
This certainly has to be a learning experience for the dev team and especially the QA team. Something is fundamentally wrong with the idea of having the Singularity test cluster, if it cannot be used to identify major, major issues like the above prior to a production release.
A sloppy, unprofessional release like this has to cause some kind of reaction internally at CCP. Something must change somehow, if we are to avoid a similar situation in the future. I'm sure players and developers alike agree with that.
Usually, testing on singularity sorts the worst things out. But before this patch, whenever i tried to login to Sissi it was either offline, or both of my accounts were stuck at login.
Singularity offline -> no bug reports makes a big diffrence from Singularity online -> no bug reports
|
|
|
| |
|